Verified Gross Mass Message - VERMAS D.16A

Verified Gross Mass Message - VERMAS D.16A - Inbound

N4 supports EDIFACT standard VERMAS message, release D & version 16A.

In relation to a supply chain including the transport of a packed container on an ocean vessel, the Verified Gross Mass message (VERMAS) permits to submit the Verified Gross Mass of the packed container and supporting information as legally required by the SOLAS Convention Chapter VI, Part A, Regulation 2.

VERMAS can be used by different parties at different times in the process chain. It is not dedicated to a particular process step in the transport chain.

VERMAS shall only be used for transmission of the SOLAS Verified Gross Mass and directly related information.

This specification provides the definition of the Verified Gross Mass message (VERMAS) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce, and transport.

The following sections of this document explain how VERMAS message is handled in N4 and scope of its implementation.

The message can be exchanged between any two parties in the maritime transport chain as per mutual agreement. The sender may have obtained the Verified Gross Mass himself or he may forward a VGM received from a 3rd party. Each party in the transport chain can be a sender or a receiver of a VERMAS message.

The VERMAS is a small message for a clearly dedicated purpose. It shall only be used for transmission of the VGM as required by SOLAS and directly related information

A VERMAS EDI may contain:

List of containers
VGM details of each container
Vessel visit information of each container

VERMAS D.16A Inbound Supported Segments

Following table illustrates the segments of EDIFACT standard VERMAS D 16B message & scope of each segment in N4

Segment Id	Supported Qualifier	Element Description	Supported in N4 ?
BGM		Beginning of Message	Following function codes are supported currently 1 - Cancellation 5 - Replace 9 - Original
DTM		Date/Time/Period To specify date, and/or time, or period.	This segment is available in .dic but not used in built-in map
RFF		Reference To specify a reference.	This segment is available in .dic but not used in built-in map
DTM		Date/Time/Period	This segment is available in .dic but not used in built-in map
NAD		Name and Address To specify the name/address and their related function, either by C082 only and/or unstructured by C058 or structured by C080 thru 3207.	This segment is available in .dic but not used in built-in map
CTA		Contact Information	This segment is available in .dic but not used in built-in map
COM		Communication Contact	This segment is available in .dic but not used in built-in map
EQD	CN	Equipment Details	supported
RFF	BN or BM	Reference	supported
LOC	9 - loadPort 11 - dischargePort1 13 - transshipPort 20 - ediCommodity-destinationPort 65 - Optional PORT2 76 - originalLoadPort 84 - not supported 85- destinationPort 88 - ediCommodity-originPort	Place/Location Identification	Following code qualifiers are supported 9, 11, 13, 20, 65, 76, 85, 88
SEL		Seal Number	supported. but only first 4 seal numbers only will be persisted into n4.
MEA	AAE	Measurements	only AET and VGM weights are supported
DTM		Date/Time/Period Date and time when gross mass was determined. In case of re-determining VGM, transmission this segment may be used to identify its latest version.	supported
TDT		Transport Information To specify information regarding the transport such as mode of transport, means of transport, its conveyance reference number and the identification of the means of transport.	Supported
RFF		Reference To specify a reference.	Supported
DOC		Document/Message Details To identify documents and details directly related to it.	This segment is available in .dic but not used in built-in map
DTM		Date/Time/Period To specify date, and/or time, or period. Date/Time when the Verified Gross Mass was determined or Date/Time when the document/certificate was issued	This segment is available in .dic but not used in built-in map
NAD		Name and Address A group to qualify and specify name and address information in VGM documentation. Group for specification of a) the party responsible of SOLAS verified gross mass declartion (SOLAS' shipper) b) the person authorized to sign VGM documents c) the weighing party for the method specified in DOC segment d) the party to be referred to for obtaining identified document e) the party which had ordered weighing at terminal or weighing station	This segment is available in .dic but not used in built-in map
CTA		Contact Information With function code RP the segment is used for transmission of a signature (person's name in capital letters).	Supported to map VGM entity/ verifier
COM		Communication Contact Contact address for party or person (according to function qualifier in current CTA group)	This segment is available in .dic but not used in built-in map

The following picture illustrates groups and their segments supported in VERMAS.

VERMAS Inbound - Message Functions

As per EDIFACT standard, Cusres has various message function codes in BGM segment. But N4 supports only Original & Update function codes.

For information on the EDI message functions supported by VERMAS, see Supported EDI message functions (on page 1).

VERMAS Inbound N4 Built-in Map

A new built-in map with map id "VERMAS_16A_IN" is added to N4. This map can be used to convert the VERMAS EDI file into Navis standard VERMAS.xml. This xml in turn used for further processing.

Following are the related files, part of N4 application and can be downloaded:

VERMAS_D_16A.mgt - GoXml map
VERMAS.dic - Edifact standard dictionary
VERMAS.xsd - Navis standard xml schema

VERMAS Inbound Samples

Original message function - One Container

Original message function - One Container but all segments

UNB+UNOA:2+APL+FCP PLANNING+030626:1314+0'
UNH+VERMAS ID+VERMAS:D:16A:UN:SMDG04'
BGM+XXX++9++39'
DTM+137:201602231537:203'
RFF+SI:T/HL007543'
DTM+171:201509160823:203'
NAD+TR+DBF:TERMINALS:306'
CTA+MS+ABC CORP.'
COM+NAME(A)LINE.COM:EM'
EQD+CN+APLU9402398:6346:5+42G1:6346:5+APL++5'
RFF+BN:APLBKG01'
LOC+9+USOAK+OAK:TERMINALS:306'
LOC+11+NZLYT+LYT:TERMINALS:306'
LOC+65+SGSIN+SIN:TERMINALS:306'
LOC+76+CNHKG+HKG:TERMINALS:306'
SEL+19876543+AA'
SEL+198765432+AB'
SEL+198765432111+CA'
SEL+198765432123+CU'
MEA+AAE+VGM+KGM:22500'
DTM+WAT:201602201632:203'
TDT+20+123+++HLC:LINES:306+++APL01::11:APL01'
RFF+VON:124'
DOC+SHP:VGM:306+27G92ZZ'
DTM+137:201602230809:203'
NAD+SPC+++BEST FRUIT LTD.+LONG STREET 987:P.O. BOX 321123+NEW YORK CITY++10007+US'
CTA+RP+:authorized person/Weighing company name'
COM+DISPATCH(A)MODERN-FOOTWEAR.COM:EM'
UNT+16179+1'
UNZ+1+0'

Replace Message Function

UNB+UNOA:2+APL+FCP PLANNING+030626:1314+0'
UNH+VERMAS ID+VERMAS:D:16A:UN:SMDG04'
BGM+XXX++5++39'
EQD+CN+APLU9402398:6346:5+42G1:6346:5+++5'
MEA+AAE+VGM+KGM:34500'
DTM+WAT:201602231632:203'
NAD+TR+DBF:TERMINALS:306'
CTA+RP+:updated3 person/Weighing company name'
UNT+16179+1'
UNZ+1+0'

Cancel message function

UNB+UNOA:2+APL+FCP PLANNING+030626:1314+0'
UNH+VERMAS ID+VERMAS:D:16A:UN:SMDG04'
BGM+XXX++1++39'
EQD+CN+APLU9402398:6346:5+42G1:6346:5+++5'
UNT+16179+1'
UNZ+1+0'

VERMAS Inbound Test Instructions

The following section explains how to setup and test a VERMAS message.

Pre-requisite for posting a VERMAS EDI message

Step - 1: Create a session for VERMAS message.

Posting a VERMAS EDI message

Step - 3: Post VERMAS Original message.

Ensure batch is completed without any error message and unit is created.

VERMAS Original message posted successfully and event is created with field changes.

Step - 4: Post VERMAS EDI Replace message

VERMAS Replace message posted successfully and VGM properties are updated, history event is recorded with field changes.

Step - 5: Post VERMAS EDI Cancel message

VERMAS Cancel message nullified weight, verified date and updated verifier. History event is recorded for cancel message with field changes.